Skip to content

chore(skills): update gh-issue-troubleshoot to commit with --no-verify#35284

Closed
dsilvam wants to merge 1 commit into
mainfrom
chore/gh-issue-troubleshoot-no-verify
Closed

chore(skills): update gh-issue-troubleshoot to commit with --no-verify#35284
dsilvam wants to merge 1 commit into
mainfrom
chore/gh-issue-troubleshoot-no-verify

Conversation

@dsilvam
Copy link
Copy Markdown
Member

@dsilvam dsilvam commented Apr 10, 2026

Summary

  • The pre-commit hook in this repo runs a full Maven build on every git commit, which takes minutes and exits non-zero even for valid commits — blocking the skill.
  • Step 7 now runs git commit --no-verify automatically instead of just printing a suggested message.
  • Added missing git tool permissions to allowed-tools (git commit, git add, git show-ref, git status, git push, git checkout).

Test plan

  • Run /gh-issue-troubleshoot on any issue — confirm it commits without triggering the Maven pre-commit hook.

🤖 Generated with Claude Code

The pre-commit hook in this repo runs a full Maven build and exits
non-zero for valid commits, blocking the skill. Always pass --no-verify
when committing from the skill. Also adds missing git tool permissions
to allowed-tools and auto-commits in Step 7 instead of just printing
a suggested message.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

  • This PR fixes #123 or Fixes: #123

  • This PR closes #123 or Closes: #123

  • This PR resolves #123 or Resolves: #123

  • Other supported keywords: fix, fixed, close, closed, resolve, resolved
    Option 2: Link via GitHub UI (Note: won't clear the failed check)

  1. Go to the PR → Development section (right sidebar)

  2. Click "Link issue" and select an existing issue

  3. Push a new commit or re-run the workflow to clear the failed check
    Option 3: Use branch naming
    Create a new branch with one of these patterns:

  • 123-feature-description (number at start)

  • issue-123-feature-description (issue-number at start)

  • feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow

@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Apr 10, 2026

Claude finished @dsilvam's task in 2m 24s —— View job


Claude finished @dsilvam's task in 1m 55s —— View job


I'll analyze this and get back to you.

@dsilvam dsilvam added this pull request to the merge queue Apr 30, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Apr 30, 2026
@dsilvam dsilvam closed this May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants